Camera tap switch

ABSTRACT

Various embodiments provide a wearable camera that can be worn by a user. The wearable camera includes an accelerometer that can be used to detect camera motion. Input can be provided to the camera in the form of one or more taps which have an associated motion profile, as sensed by the accelerometer. The tap or taps can be mapped to camera functionality to activate the functionality.

BACKGROUND

Physical buttons are not always an appealing feature to add to hardware,such as a camera. This is particularly true when the hardware or camerahas a small form factor. Additional physical buttons can create acrowding situation on the hardware or camera and can lead to anunaesthetic appearance. Further, crowded buttons increase the likelihoodthat a user will inadvertently press the wrong button.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter.

Various embodiments provide a wearable camera that can be worn by auser. The wearable camera includes an accelerometer that can be used todetect camera motion. Input can be provided to the camera in the form ofone or more taps which have an associated motion profile, as sensed bythe accelerometer. The tap or taps can be mapped to camera functionalityto activate the functionality.

In at least some embodiments, different combinations of taps can bemapped to different camera functionality. Further, in at least someembodiments, the camera includes a microphone which detects sound aroundthe camera. The microphone can be used to sense a noise profileassociated with the tap or taps that are received by the camera. Thenoise profile can be used, together with the motion profile, to confirmthe input as a tap input.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description references the accompanying figures. In thefigures, the left-most digit(s) of a reference number identifies thefigure in which the reference number first appears. The use of the samereference numbers in different instances in the description and thefigures may indicate similar or identical items.

FIG. 1 is an example camera device in accordance with one or moreembodiments.

FIG. 2 illustrates an example camera device in accordance with one ormore embodiments.

FIG. 3 illustrates an example camera device in accordance with one ormore embodiments.

FIG. 4 is a flow diagram that describes steps in a method in accordancewith one or more embodiments.

FIG. 5 is a flow diagram that describes steps in a method in accordancewith one or more embodiments.

FIG. 6 is a flow diagram that describes steps in a method in accordancewith one or more embodiments.

FIG. 7 is a flow diagram that describes steps in a method in accordancewith one or more embodiments.

FIG. 8 is a flow diagram that describes steps in a method in accordancewith one or more embodiments.

FIG. 9 is a flow diagram that describes steps in a method in accordancewith one or more embodiments.

DETAILED DESCRIPTION

Overview

Various embodiments provide a wearable camera that can be worn by auser. The wearable camera includes an accelerometer that can be used todetect camera motion. Input can be provided to the camera in the form ofone or more taps which have an associated motion profile, as sensed bythe accelerometer. The tap or taps can be mapped to camera functionalityto activate the functionality. Any suitable type of functionality can bemapped to the tap or taps.

In at least some embodiments, different combinations of taps can bemapped to different camera functionality. Further, in at least someembodiments, the camera includes a microphone which detects sound aroundthe camera. The microphone can be used to sense a noise profileassociated with the tap or taps that are received by the camera. Thenoise profile can be used, together with the motion profile, to confirmthe input as a tap input. This can help to disambiguate various othertypes of input that might be received by the camera. For example, theuser may be wearing the camera and may jump up and down. The jump mayhave a motion profile that is similar to that of a tap. By looking for anoise profile associated with a tap when a tap-like motion profile isreceived, the camera can confirm whether or not the received input is atap.

The camera can be worn in any suitable location. For example, the cameracan be worn on a user's head such as, a way of example and notlimitation, a hat-mounted camera, glasses-mounted camera,headband-mounted camera, helmet-mounted camera, and the like.Alternately or additionally, the camera can be worn on locations otherthan the user's head. For example, the camera can be configured to bemounted on the user's clothing.

Various other embodiments provide a wearable camera that is mountable ona user's clothing. The camera is designed to be unobtrusive anduser-friendly insofar as being mounted away from the user's face so asnot to interfere with their view. In at least some embodiments, thecamera includes a housing and a clip mounted to the housing to enablethe camera to be clipped onto the user's clothing. The camera isdesigned to be lightweight with its weight balanced in a manner that istoward the user when clipped to the user's clothing.

In one or more embodiments, the camera includes a replay mode. When thereplay mode is selected, the camera automatically captures image data,such as video or still images, and saves the image data to a memorybuffer. In at least some embodiments, the size of the memory buffer canbe set by the user to determine how much image data is to be collected.Once the memory buffer is full, the older image data is erased to makeroom for currently-captured image data. If an event occurs that the userwishes to memorialize through video or still images, a record button canbe activated which saves the image data from the beginning of the memorybuffer and continues recording until the user presses the record buttonagain. In this manner, if an event occurs, the user is assured ofcapturing the event from a time t-x, where x is the length of the memorybuffer, in time.

In the discussion that follows, a section entitled “Example Environment”describes an example environment in which the various embodiments can beutilized. Next, a section entitled “Replay Functionality” describes anexample replay mode in accordance with one or more embodiments.Following this, a section entitled “Duel Encoding” describes anembodiment in which captured image data can be dual encoded inaccordance with one or more embodiments. Next, a section entitled “PhotoLog” describes an example photo log in accordance with one or moreembodiments. Following this, a section entitled “Camera Tap Switch”describes a camera tap switch in accordance with one or moreembodiments.

Consider now an example environment in which various embodiments can bepracticed.

Example Environment

FIG. 1 illustrates a schematic of a camera device 100 in accordance withone or more embodiments. The camera device 100 includes a lens 102having a focal length that is suitable for covering a scene to bepictured. In one embodiment, a mechanical device may be included withthe lens 102 to enable auto or manual focusing of the lens. In anotherembodiment, the camera device 100 may be a fixed focus device in whichno mechanical assembly is included to move the lens 102. A sensor 104having a sensing surface (not shown) is also included to convert animage formed by the incoming light on the sensing surface of the sensor104 into a digital format. The sensor 104 may include a charge-coupleddevice (CCD) or complementary metal oxide semiconductor (CMOS) imagesensor for scanning the incoming light and creating a digital picture.Other technologies or devices may be used so long as the used device iscapable of converting an image formed by the incoming light on a sensingsurface into the digital form. Typically, these image detection devicesdetermine the effects of light on tiny light sensitive devices andrecord the changes in a digital format.

It should be appreciated that the camera device 100 may include othercomponents such as a battery or power source and other processorcomponents that are required for a processor to operate. However, toavoid obfuscating the teachings, these well-known components are beingomitted. In one embodiment, the camera device 100 does not include aview finder or a preview display. In other embodiments, however, apreview display may be provided. The techniques described herein can beused in any type of camera, and are particularly effective in small,highly portable cameras, such as those implemented in mobile telephonesand other portable user equipment. Thus, in one embodiment, the cameradevice 100 includes hardware or software for making and receiving phonecalls. Alternately, the camera device 100 can be a dedicated,stand-alone camera.

In at least some embodiments, the camera device 100 further includes amotion detector 108 that can include an accelerometer and, in someembodiments, a gyroscope. The accelerometer is used for determining thedirection of gravity and acceleration in any direction. The gyroscopemay also be used either in addition to the accelerometer or instead ofthe accelerometer. The gyroscope can provide information about how therotational angle of the camera device 100 changes over time. Any othertype of sensor may be used to detect the camera's motion. Using therotational angle, an angle of rotation of the camera device 100 may becalculated, if the camera device 100 is rotated. In at least someembodiments, input can be provided to the camera in the form of one ormore taps which have an associated motion profile, as sensed by theaccelerometer. The tap or taps can be mapped to camera functionality toactivate the functionality. Any suitable type of functionality can bemapped to the tap or taps.

In at least some embodiments, different combinations of taps can bemapped to different camera functionality. Further, in at least someembodiments, the camera includes a microphone which detects sound aroundthe camera. The microphone can be used to sense a noise profileassociated with the tap or taps that are received by the camera. Thenoise profile can be used, together with the motion profile, to confirmthe input as a tap input. This can help to disambiguate various othertypes of input that might be received by the camera, as noted above andbelow.

Further included is an input/output (I/O) port 114 for connecting thecamera device 100 to an external device, including a general purposecomputer. The I/O port 114 may be used for enabling the external deviceto configure the camera device 100 or to upload/download data. In oneembodiment, the I/O port 114 may also be used for streaming video orpictures from the camera device 100 to the external device. In oneembodiment, the I/O port may also be used for powering the camera device100 or charging a rechargeable battery (not shown) in the camera device100.

The camera device 100 may also include an antenna 118 that is coupled toa transmitter/receiver (Tx/Rx) module 116. The Tx/Rx module 116 iscoupled to a processor 106. The antenna 118 may be fully or partlyexposed outside the body of the camera device 100. However, in anotherembodiment, the antenna 118 may be fully encapsulated within the body ofthe camera device 100. The Tx/Rx module 116 may be configured for Wi-Fitransmission/reception, Bluetooth transmission/reception or both. Inanother embodiment, the Tx/Rx module 116 may be configured to use aproprietary protocol for transmission/reception of the radio signals. Inyet another embodiment, any radio transmission or data transmissionstandard may be used so long as the used standard is capable oftransmitting/receiving digital data and control signals. In oneembodiment, the Tx/Rx module 116 is a low power module with atransmission range of less than ten feet. In another embodiment, theTx/Rx module 116 is a low power module with a transmission range of lessthan five feet. In other embodiments, the transmission range may beconfigurable using control signals received by the camera device 100either via the I/O port 114 or via the antenna 118.

The camera device 100 further includes a processor 106. The processor106 is coupled to the sensor 104 and the motion detector 108. Theprocessor 106 may also be coupled to storage 110, which, in oneembodiment, is external to the processor 106. The storage 110 may beused for storing programming instructions for controlling and operatingother components of the camera device 100. The storage 110 may also beused for storing captured media (e.g., pictures and/or videos). Inanother embodiment, the storage 110 may be a part of the processor 106itself.

In one embodiment, the processor 106 may include an image processor 112.The image processor 112 may be a hardware component or may also be asoftware module that is executed by the processor 106. It may be notedthat the processor 106 and/or the image processor 112 may reside indifferent chips. For example, multiple chips may be used to implementthe processor 106. In one example, the image processor 112 may be aDigital Signal Processor (DSP). The image processor can be configured asa processing module, that is a computer program executable by aprocessor. In at least some embodiments, the processor 112 is used toprocess a raw image received from the sensor 104 based, at least inpart, on the input received from the motion detector 108. Othercomponents such as Image Signal Processor (ISP) may be used for imageprocessing.

In one embodiment, the storage 110 is configured to store both raw(unmodified image) and the corresponding modified image. In one or moreembodiments, the storage 110 can include a memory buffer, such as aflash memory buffer, that can be used as a circular buffer to facilitatecapturing image data when the camera is set to a replay mode that issupported by replay module 120. The replay module 120 can be implementedin connection with any suitable hardware, software, firmware, orcombination thereof. When the replay mode is selected, the cameraautomatically captures image data, such as video or still images, andsaves the image data to the memory buffer. In at least some embodiments,the size of the memory buffer can be set by the user to determine howmuch image data is to be collected. If an event occurs that the userwishes to memorialize through video or still images, a record button canbe activated which saves the image data from the beginning of the memorybuffer and continues recording until the user presses the record buttonagain. In this manner, if an event occurs, the user is assured ofcapturing the event from a time t-x, where x is the length of the memorybuffer, in time.

A processor buffer (not shown) may also be used to store the image data.The pictures can be downloaded to the external device via the I/O port114 or via the wireless channels using the antenna 118. In oneembodiment, both unmodified and modified images are downloaded to theexternal device when the external device sends a command to downloadimages from the camera device 110. In one embodiment, the camera device100 may be configured to start capturing a series of images at aselected interval.

In one embodiment, a raw image from the sensor 104 is inputted to animage processor (such as an ISP) for image processing or blur detection.After image processing is applied to the image outputted by the imageprocessor, the modified image is encoded. The image encoding istypically performed to compress the image data.

In an example embodiment, the camera device 100 may not include thecomponents for processing the image captured by the sensor 104. Instead,the camera device 100 may include programming instructions to transmitthe raw image after extracting the image from the sensor 104 to a cloudbased processing system that is connected to the camera device 100 viathe Internet or a local area network. The cloud based system isconfigured to receive the raw image and process the image or images asdescribed above and below. The encoded image is then either stored in aselected cloud based storage or the image is sent back to the cameradevice 100 or to any other device according to a user configuration. Theuse of a cloud based image processing system can reduce a need forincorporating several image processing components in each camera device,thus making a camera device lighter, more energy efficient and cheaper.

In another example embodiment, instead of a cloud based imageprocessing, the camera device 100 may send either a raw image or theimage processed through an image processor to another device, e.g., amobile phone or a computer. The image may be transmitted to the mobilephone (or a computer) for further processing via Wi-Fi, Bluetooth or anyother type of networking protocol that is suitable for transmittingdigital data from one device to another device. After the mobile devicereceives the image or images, according to one or more embodimentsdescribed herein, the produced image may be saved to local storage onthe device, transferred for storage in a cloud based storage system, ortransmitted to another device, according to user or systemconfigurations.

In one embodiment, the native image processing system in the cameradevice 100 may produce images and/or videos in a non-standard format.For example, a 1200×1500 pixel image may be produced. This may be doneby cropping, scaling, or using an image sensor with a non-standardresolution. Since methods for transforming images in a selected standardresolution are well-known, there will be no further discussion on thistopic.

Various embodiments described above and below can be implementedutilizing a computer-readable storage medium that includes instructionsthat enable a processing unit to implement one or more aspects of thedisclosed methods as well as a system configured to implement one ormore aspects of the disclosed methods. By “computer-readable storagemedium” is meant all statutory forms of media. Accordingly,non-statutory forms of media such as carrier waves and signals per seare not intended to be covered by the term “computer-readable storagemedium”.

As noted above, camera device 100 can assume any suitable form ofwearable camera. The camera can be worn in any suitable locationrelative to a user. For example, the camera can be worn on a user's headsuch as, by a way of example and not limitation, a hat-mounted camera,glasses-mounted camera, headband-mounted camera, helmet-mounted camera,and the like. Alternately or additionally, the camera can be worn onlocations other than the user's head. For example, the camera can beconfigured to be mounted on the user's clothing or other items carriedby a user, such as a backpack, purse, briefcase, and the like.

In the example provided just below, a wearable camera is described inthe context of a camera that is mountable on the user's clothing. It isto be appreciated and understood, however, that other types ofnon-clothing mountable, wearable cameras can be utilized withoutdeparting from the spirit and scope of the claimed subject matter.

Moving on to FIGS. 2 and 3, consider the following. FIG. 2 illustratesan example camera device 200 in a front elevational view, while FIG. 3illustrates the camera device 200 in a side elevational view. The cameradevice 200 includes a housing 202 that contains the components describedin FIG. 1. Also illustrated is a camera lens 204 (FIG. 2) and afastening device 300 (FIG. 3) in the form of a clip that operates in amanner that is similar to a clothespin. Specifically, the fasteningdevice 300 includes a prong 302 with a body having a thumb-engageableportion 304. The body extends along an axis away from thethumb-engageable portion 304 toward a distal terminus 306. A springmechanism, formed by the body or separate from and internal relative tothe body, enables prong 302 to be opened responsive to pressure beingapplied to the thumb-engageable portion 304. When opened, a piece ofclothing can be inserted into area 308. When the thumb-engageableportion 304 is released, the clothing is clamped in place by the prong302 thereby securely mounting the camera device on a piece of clothing.For example, the camera device can be mounted, as described above, on anecktie, blouse, shirt, pocket, and the like.

In addition, camera device 200 can include a number of input buttonsshown generally at 310. The input buttons can include, by way of exampleand not limitation, an input button to take a still picture, an inputbutton to initiate the replay mode, an input button to initiate a videocapture mode, and an input button to enable the user to adjust thebuffer size that is utilized during the replay mode. It is to beappreciated and understood that the various input buttons can be locatedanywhere on the camera device 200.

It may be noted that even though the camera device 200 is shown to havea particular shape, the camera device 100 can be manufactured in anyshape shape and size suitable and sufficient to accommodate the abovedescribed components of the camera device 100. The housing 202 of thecamera device may be made of a metal molding, a synthetic materialmolding or a combination thereof. In other embodiments, any suitabletype of material may be used to provide a durable and strong outer shellfor typical portable device use.

In addition, the fastening device 300 can comprise any suitable type offastening device. For example, the fastening device may be a simpleslip-on clip, a crocodile clip, a hook, a Velcro or a magnet or a pieceof metal to receive a magnet. The camera device 200 may be affixedpermanently or semi-permanently to another object using the fasteningdevice 300.

Generally, any of the functions described herein can be implementedusing software, firmware, hardware (e.g., fixed logic circuitry), or acombination of these implementations. The terms “module,”“functionality,” “component” and “logic” as used herein generallyrepresent software, firmware, hardware, or a combination thereof. In thecase of a software implementation, the module, functionality, or logicrepresents program code that performs specified tasks when executed on aprocessor (e.g., CPU or CPUs). The program code can be stored in one ormore computer readable memory devices. The features of the techniquesdescribed below are platform-independent, meaning that the techniquesmay be implemented on a variety of commercial computing platforms havinga variety of processors.

For example, the camera device 200 may include a computer-readablemedium that may be configured to maintain instructions that cause thecamera's software and associated hardware to perform operations. Thus,the instructions function to configure the camera's software andassociated hardware to perform the operations and in this way result intransformation of the software and associated hardware to performfunctions. The instructions may be provided by the computer-readablemedium to the camera device through a variety of differentconfigurations.

One such configuration of a computer-readable medium is signal bearingmedium and thus is configured to transmit the instructions (e.g., as acarrier wave) to the camera device, such as via a network. Thecomputer-readable medium may also be configured as a computer-readablestorage medium and thus is not a signal bearing medium. Examples of acomputer-readable storage medium include a random-access memory (RAM),read-only memory (ROM), an optical disc, flash memory, hard disk memory,and other memory devices that may use magnetic, optical, and othertechniques to store instructions and other data.

Having considered an example operating environment in accordance withone or more embodiments, consider now a discussion of replayfunctionality and other features that can be provided by the cameradevice.

Replay Functionality

As noted above, camera device 200 includes a replay mode. When thereplay mode is selected, as by the user pressing an input buttonassociated with initiating the replay mode, the camera automaticallycaptures image data, such as video or still images, and saves the imagedata to a memory buffer. In one or more embodiments, the memory bufferis a circular buffer that saves an amount of image data, for examplevideo data. When the memory buffer is full of image data, it deletes theoldest image data to make room for newly recorded image data. Thiscontinues until either the user exits the replay mode or presses abutton associated with initiating video capture, i.e. the “record”button.

In at least some embodiments, the size of the memory buffer can be setby the user to determine how much image data is to be collected. As anexample, the user might set the length of the memory buffer tocorrespond to 5 seconds, 30 seconds, 1 minute, 2 minutes, and longer.

Assume now that an event occurs that the user wishes to memorializethrough video or still images. Assume also that the user has initiatedthe replay mode so that video data is currently being buffered in thememory buffer. By pressing the “record” button the video data is nowsaved from the beginning of the memory buffer and recording continuesuntil the user presses the record button again. In this manner, if anevent occurs, the user is assured of capturing the event from a timet-x, where x is the length of the memory buffer, in time. So, forexample, if the user initially set the memory buffer to capture 2minutes worth of video data, by pressing the “record” button, the last 2minutes of video data will be recorded in addition to the currentlyrecorded video data.

In one or more embodiments, the memory buffer comprises flash memory.When the user presses the “record” button and the camera device is inreplay mode, a pointer is used to designate where, in flash memory, thebeginning of the captured video data occurs, e.g., the beginning of thelast 2 minutes of video data prior to entering the “record” mode. Inother embodiments, the video data captured during replay mode and“record” mode can be written to an alternate storage location.

FIG. 4 is a flow diagram that describes steps in a method in accordancewith one or more embodiments. The method can be performed in connectionwith any suitable hardware, software, firmware, or combination thereof.In at least some embodiments, the method is performed by asuitably-configured camera device such as the one described above.

Step 400 receives input associated with a replay mode. This step can beperformed in any suitable way. For example, in at least someembodiments, this step can be performed by receiving input from the uservia a suitable input device on the camera device. Responsive toreceiving the input associated with the replay mode, step 402 capturesimage data and saves the image data to a memory buffer. Step 404ascertains whether the buffer is full. If the buffer is not full, themethod returns to step 402 and continues to capture image data and saveimage data to the memory buffer. If, on the other hand, the buffer isfull, step 406 deletes the oldest image data in the memory buffer andreturns to step 402 to capture subsequent image data.

This process continues until either the user presses the “record” buttonor exits the replay mode.

FIG. 5 is a flow diagram that describes steps in another method inaccordance with one or more embodiments. The method, which allows a userto set the camera device's memory buffer size, can be performed inconnection with any suitable hardware, software, firmware, orcombination thereof. In at least some embodiments, the method isperformed by a suitably-configured camera device such as the onedescribed above.

Step 500 receives input to set a memory buffer size. The step can beperformed in any suitable way. For example, in at least someembodiments, the step can be performed by receiving user input by way ofa suitably-configured input mechanism such as a button on the cameradevice. Responsive to receiving this input, step 502 sets the memorybuffer size.

Step 504 receives input associated with a replay mode. This step can beperformed in any suitable way. For example, in at least someembodiments, this step can be performed by receiving input from the uservia a suitable input device on the camera device. Responsive toreceiving the input associated with the replay mode, step 506 capturesimage data and saves the image data to a memory buffer. Step 508ascertains whether the buffer is full. If the buffer is not full, themethod returns to step 506 and continues to capture image data and saveimage data to the memory buffer. If, on the other hand, the buffer isfull, step 510 deletes the oldest image data in the memory buffer andreturns to step 506 to capture subsequent image data.

This process continues until either the user presses the “record” buttonor exits the replay mode.

FIG. 6 is a flow diagram that describes steps in another method inaccordance with one or more embodiments. The method can be performed inconnection with any suitable hardware, software, firmware, orcombination thereof. In at least some embodiments, the method isperformed by a suitably-configured camera device such as the onedescribed above.

Step 600 captures image data and saves the image data to a memorybuffer. The step can be performed in any suitable way. For example, thestep can be performed as described in connection with FIG. 4 or 5. Step602 receives input to enter the camera device's record mode. This stepcan be performed, for example, by receiving user input by way of a“record” button. Responsive to receiving the input to enter record mode,step 604 saves image data from the beginning of the memory buffer. Thisstep can be performed in any suitable way. For example, the step can beperformed by setting a pointer to point to the beginning of the memorybuffer. Step 606 saves currently captured image data in addition to theimage data from the beginning of the memory buffer. This step can beperformed until the user presses the “record” button once more.

Having considered an example replay mode and how it can be implementedwith a suitably hiding configured camera device, consider now aspects ofa dual encoding process.

Dual Encoding

In one or more embodiments, the camera device's processor 106 (FIG. 1)is configured to encode image data at different levels of resolution.For example, the camera device can encode image data at a low level ofresolution and at a high level of resolution as well. Any suitablelevels of resolution can be utilized. In at least some embodiments, thelow level of resolution is Quarter-VGA (e.g., 320×240) and the highlevel of resolution is 720 p (e.g., 1280×720).

Encoding image data at different resolutions levels can enhance theuser's experience insofar as giving the user various options to transferthe saved image data. For example, at lower resolution levels, thecaptured image data can be streamed to a device such as a smart phone.Alternately or additionally, at higher resolution levels, when the userhas Wi-Fi accessibility, they can transfer the image data to a networkdevice such as a laptop or desktop computer.

Having considered a dual encoding scenario, consider now aspects of aphoto log that can be constructed using the principles described above.

Photo Log

Photo log refers to a feature that enables a user to log their day instill photos at intervals of their own choosing. So, for example, if theuser wishes to photo log their day at every 3 minutes, they can provideinput to the camera device so that every 3 minutes the cameraautomatically takes a still photo and saves it. At the end of the day,the user will have documented their day with a number of different stillphotos.

In at least some embodiments, the photo log feature can work in concertwith the replay mode described above. For example, if the user hasentered the replay mode by causing image data to be captured and savedto the memory buffer, the camera device's processor can process portionsof the captured video data at defined intervals to provide the stillphotos. This can be performed in any suitable way. For example, thecamera device's processor can process the video data on the camera'sphotosensor and read predefined areas of the photosensor to process theread areas into the still photos. In some instances the photo format isa square format so that the aspect ratio is different from that aspectratio of the video data.

Having considered an example photo log feature, consider now how thisfeature can be used in connection with the camera embodiments describedbelow.

Accelerometer-Based Camera Tap Switch

As noted above, input can be received by the camera in the form of oneor more taps which have an associated motion profile, as sensed by theaccelerometer. The tap can occur at any suitable location on thecamera's housing. In at least some embodiments, a dedicated tap area maybe provided and may have characteristics to facilitate detection. Thesecharacteristics may include, by way of example and not limitation, beingformed from a material that produces a richer or more identifiableprofile. The tap or taps can be mapped to camera functionality toactivate the functionality. Any suitable type of functionality can bemapped to the tap or taps. For example, in at least some embodiments, atap or taps can be mapped to functionality that enables video taken bythe camera to be bookmarked. For example, assume that a user is wearingthe camera and has placed a camera into a photo log mode thatautomatically captures video. At some point, something interesting mayoccur in the video that the user wishes to bookmark. At this point, ifthe user taps the camera housing, the camera can detect the tap and takesteps to bookmark the video.

FIG. 7 is a flow diagram that describes steps in another method inaccordance with one or more embodiments. The method can be performed inconnection with any suitable hardware, software, firmware, orcombination thereof. In at least some embodiments, the method isperformed by a suitably-configured camera device such as the onedescribed above.

Step 700 receives one or more motion inputs. Step 702 ascertains whetherthe one or more motion inputs are a tap or taps, respectively. This stepcan be performed in any suitable way. In at least some embodiments, thestep is performed through the use of an accelerometer. Specifically, atap or taps can have an associated profile or profiles as represented byaccelerometer data. These profiles can be stored on the camera device instorage, such as storage 110. When the motion input is received, theaccelerometer can detect the motion and produce associated accelerometerdata. The camera's processor can then analyze the accelerometer dataassociated with the motion input and look for a particular storedprofile associated with the tap or taps. If an input is received thathas a profile that matches or resembles the stored tap profile(s) to acertain degree, the processor can ascertain that the input is a tap.

Responsive to the input(s) being a tap or taps, step 704 accesses acamera functionality that is associated with the input that wasreceived. As noted above, any suitable type of functionality can beaccessed. In at least some embodiments, such functionality isfunctionality that enables video, currently being taken by the camera,to be bookmarked. Step 706 activates the camera functionality. This stepcan be performed in any suitable way. For example, where the camerafunctionality bookmarks video taken by the camera, the step can beperformed by actually bookmarking the video data.

In at least some embodiments, different combinations of taps can bemapped to different camera functionality. Thus, a single tap might bemapped to a first functionality, a double tap might be mapped to asecond functionality, a triple tap might be mapped to a thirdfunctionality, and so on. Further, different tap patterns can be mappedto different functionalities. For example, two taps in rapid successionfollowed by a third somewhat delayed tap might be mapped to onefunctionality while a single tap followed by two taps in rapidsuccession might be mapped to another different functionality.

FIG. 8 is a flow diagram that describes steps in another method inaccordance with one or more embodiments. The method can be performed inconnection with any suitable hardware, software, firmware, orcombination thereof. In at least some embodiments, the method isperformed by a suitably-configured camera device such as the onedescribed above.

Step 800 receives one or more motion inputs. Step 802 ascertains whetherthe one or more motion inputs are a tap or taps, respectively. This stepcan be performed in any suitable way. In at least some embodiments, thisstep is performed through the use of an accelerometer. Specifically, atap or taps can have an associated profile or profiles as represented byaccelerometer data. These profiles can be stored on the camera device instorage, such as storage 110. When the motion input is received, theaccelerometer can detect the motion and produce associated accelerometerdata. The camera's processor can then analyze the accelerometer dataassociated with the motion input and look for a particular storedprofile associated with the tap or taps. If an input is received thathas a profile that matches or resembles the stored tap profile(s) to acertain degree, the processor can ascertain that the input is a tap.

Step 804 maps the tap or taps to a particular functionality.Specifically, in this embodiment, different combinations of taps can bemapped to different functionalities, respectively. Accordingly, thisstep ascertains which of a number of different functionalities the tapor taps are associated with.

Responsive to ascertaining which functionality is associated with thetap or taps, step 806 accesses the camera functionality that isassociated with the input that was received. As noted above, anysuitable type of functionality can be accessed. Step 808 activates thecamera functionality. This step can be performed in any suitable way.

Further, in at least some embodiments, the camera includes a microphonewhich detects sound around the camera. The microphone can be used tosense or create a noise profile associated with motion input that isreceived by the camera. The noise profile can be used, together with themotion profile, to confirm whether or not the motion input is a tapinput. This can help to disambiguate various other types of input thatmight be received by the camera. For example, the user may be wearingthe camera and may jump up and down. The jump may have a motion profilethat is similar to that of a tap. However, the jump also has a noiseprofile. By capturing the noise profile of the jump and comparing itwith noise profiles of known taps that can be stored on the camera, thecamera can confirm whether or not the received motion input is a tap.For example, while the motion profile of the jump may be similar to thatof a tap, if the noise profile of the jump is different from that of thetap, the camera can conclude that the motion input is not, in fact, atap.

FIG. 9 is a flow diagram that describes steps in another method inaccordance with one or more embodiments. The method can be performed inconnection with any suitable hardware, software, firmware, orcombination thereof. In at least some embodiments, the method isperformed by a suitably-configured camera device such as the onedescribed above.

Step 900 receives one or more motion inputs. Step 902 receives noiseinput associated with the motion input. The step can be performed usingthe camera's microphone. Step 904 ascertains whether the one or moremotion inputs are a tap or taps, respectively. This step can beperformed in any suitable way. In at least some embodiments, this stepis performed through the use of an accelerometer and a microphone.Specifically, a tap or taps have a particular motion profile that isrepresented by accelerometer data and stored on the camera device.Further, the tap or taps have a particular noise profile that is alsostored on the camera device. When the motion input is received, thecamera's processor can analyze the accelerometer data and the noiseinput that is received and derive motion and noise profiles from thedata, and then look for a stored tap profile for a match (both motionand noise). If an input is received that has a motion profile and noiseprofile that matches or resembles the tap profile to a certain degree,the processor can ascertain that the input is a tap.

Step 906 maps the tap or taps to a particular functionality.Specifically, in some embodiments, different combinations of taps aremapped to different functionalities respectively. Accordingly, this stepcan ascertain which of a number of different functionalities the tap ortaps are associated with. Alternately, a single camera functionality,such as bookmarking a video, may be associated with tap input. In thiscase, the tap or taps are mapped to the single functionality.

Responsive to ascertaining which functionality is associated with thetap or taps, step 908 accesses the camera functionality that isassociated with the input that was received. As noted above, anysuitable type of functionality can be accessed. Step 910 activates thecamera functionality. This step can be performed in any suitable way.

CONCLUSION

Various embodiments provide a wearable camera that can be worn by auser. The wearable camera includes an accelerometer that can be used todetect camera motion. Input can be provided to the camera in the form ofone or more taps which have an associated motion profile, as sensed bythe accelerometer. The tap or taps can be mapped to camera functionalityto activate the functionality.

In at least some embodiments, different combinations of taps can bemapped to different camera functionality. Further, in at least someembodiments, the camera includes a microphone which detects sound aroundthe camera. The microphone can be used to sense a noise profileassociated with the tap or taps that are received by the camera. Thenoise profile can be used, together with the motion profile, to confirmthe input as a tap input.

Although the embodiments have been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the various embodiments defined in the appended claims are notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as example forms ofimplementing the various embodiments.

What is claimed is:
 1. A wearable device comprising: a housing, thehousing comprising a dedicated tap area having characteristics tofacilitate detection of taps to the dedicated tap area; a camera lenssupported by the housing and configured to enable capture of image data;a fastening device on the housing and configured to enable the wearabledevice to be worn by a user; a motion detector configured to receive oneor more motion inputs; a processor configured to: ascertain whether theone or more motion inputs are a tap or taps to the dedicated tap area,respectively; responsive to the one or more motion inputs being a tap ortaps to the dedicated tap area, access a camera functionality that isassociated with the tap or taps; and activate the camera functionality.2. The wearable device of claim 1, wherein the motion detector comprisesan accelerometer.
 3. The wearable device of claim 1, wherein the motiondetector comprises an accelerometer and wherein the processor isconfigured to ascertain whether the one or more motion inputs are a tapor taps by analyzing the accelerometer data to ascertain whether aprofile associated with the one or more motion inputs matches orresembles one or more stored tap profiles.
 4. The wearable device ofclaim 1, wherein the camera functionality comprises functionalityenabling video to be bookmarked.
 5. The wearable device of claim 1,wherein the processor is further configured to enable the wearabledevice to enter a camera mode that enables video to be automaticallycaptured.
 6. The wearable device of claim 1, wherein the processor isfurther configured to enable the wearable device to enter a camera modethat enables video to be automatically captured and wherein the camerafunctionality comprises functionality enabling the video to bebookmarked.
 7. The wearable device of claim 1, wherein different tappatterns are mapped to different camera functionalities.
 8. Acomputer-implemented method comprising: entering a camera mode thatenables video to be automatically captured; receiving, with a wearabledevice, one or more motion inputs; ascertaining whether the one or moremotion inputs are a tap or taps, respectively; responsive to the one ormore motion inputs being a tap or taps, accessing a camera functionalitythat enables the automatically captured video to be bookmarked, thecamera functionality associated with the tap or taps; and activating thecamera functionality.
 9. The method of claim 8, wherein saidascertaining is performed using an accelerometer on the wearable device.10. The method of claim 8, wherein said ascertaining is performed by:detecting the one or more motion inputs using an accelerometer;producing associated accelerometer data; and analyzing the accelerometerdata to ascertain whether a profile associated with the one or moremotion inputs matches or resembles one or more stored tap profiles. 11.The method of claim 8, wherein the wearable device is configured to beworn on a location other than a user's clothing.
 12. The method of claim8, wherein different patterns are mapped to different camerafunctionalities.
 13. A wearable device comprising: a housing; a cameralens supported by the housing and configured to enable capture of imagedata; a fastening device on the housing and configured to enable thewearable device to be worn by a user; an accelerometer configured toreceive one or more motion inputs; a microphone configured to enable anoise profile associated with the one or more motion inputs to becreated; a processor configured to: ascertain, using the accelerometerand the microphone, whether the one or more motion inputs are a tap ortaps, respectively by: analyzing accelerometer data of the one or moremotion inputs to ascertain whether a profile associated with the one ormore motion inputs matches or resembles one or more stored tap profiles;and responsive to determining that the profile associated with the oneor more motion inputs matches or resembles one or more stored tapprofiles, analyzing microphone data associated with the one or moremotion inputs to ascertain whether the noise profile associated with theone or more motion inputs matches or resembles one or more stored noisetap profiles; responsive to the one or more motion inputs being a tap ortaps, access a camera functionality that is associated with the tap ortaps; and activate the camera functionality, wherein the camerafunctionality includes functionality enabling the video to bebookmarked.
 14. The wearable device of claim 13, wherein the fasteningdevice is configured to enable the wearable device to be mounted onclothing.
 15. The wearable device of claim 13, wherein the fasteningdevice is configured to enable the wearable device to be mounted on alocation other than a user's clothing.
 16. The wearable device of claim13, wherein the processor is further configured to enable the wearabledevice to enter a camera mode that enables video to be automaticallycaptured.
 17. The wearable device of claim 13, wherein the processor isfurther configured to enable the wearable device to enter a camera modethat enables video to be automatically captured.
 18. The wearable deviceof claim 13, wherein the housing includes a dedicated tap area havingcharacteristics to facilitate detection of taps to the dedicated taparea.